The suite stayed green through the whole window in which `src/` applied no
rotary, and it would have stayed green after a fix that pairs the wrong dims.
Both have the same cause: every container the suite can reach is a Kimi, every
Kimi sets `mla_use_nope`, and so nothing in `tests/` ever entered `rope_init` or
`rope_apply`. This is the missing half of the previous commit.

`make_test_container.py --rope` writes a DeepSeek-V3 at the 1/18 scale the file
already builds a Kimi-Linear at: no `mla_use_nope`, `rope_theta` and the YaRN
block copied from Kimi-K2-Instruct's config, and no `linear_attn_config` at all,
which is what makes every layer MLA. All-MLA is deliberate twice over — it
exercises the rotation at depth rather than in the single full-attention layer
the Kimi mix leaves, and it is the shape `deepseek_ref.py` can read, since not
indexing `linear_attn_config` is exactly what separates it from `kimi_ref.py`.
K2's rope block rather than V3's because `beta_fast == beta_slow == 1.0`
collapses YaRN's correction range to a two-dim ramp, which is the more awkward
of the two to get right.

The checks build their own container instead of using `$MODEL`, so they run on
every host and do not wait on weights nobody can convert yet — sqliteai#26 is what makes
a real V3 container, and the shape is what the engine branches on.

  - rotated MLA against the PyTorch oracle
  - chunked prefill == token-at-a-time with rotation, which holds by
    construction today because `mla_layer` is per-token on both paths, and is
    exactly the "by construction" a later batched MLA would break quietly
  - a rope slice wider than `WASTE_MAX_ROPE_HALF` is refused at load

The first takes the same two-source shape as the Kimi oracle above it:
generate from `deepseek_ref.py` where `uv` exists, fall back to a fixture where
it does not, so the Linux image without `uv` runs it rather than skipping it.
Unlike that one the fixture ships, because this container is generated rather
than converted and so is byte-reproducible at `--seed 0` — the sidecar carries a
digest of the container it was made from, so a later change to the generator's
weights reads as "regenerate me" and not as an engine bug. The fixture is the
reference's logits, never the engine's.

`deepseek_ref.py` grows the `--dump` that `kimi_ref.py` already had, so the diff
is over whole logit vectors and not a printed top-k.

Verified by reverting `src/model.c` and `src/model.h` to their pre-fix state
with `tests/` and `tools/` left alone: the oracle check and the refusal check
both fail, which is the property that makes them worth having. Both fallback
paths were exercised directly — `uv` off `PATH` passes against the fixture, and
a corrupted digest skips with the regenerate message instead of reporting a
divergence.

`set -o pipefail` sank the refusal check on the first run, because a refused
load exits non-zero and that is the point; the output is read into a variable
now, with a comment saying why.

Suite on this commit: 46 passed, 0 failed, 2 skipped against Kimi-Linear and K3
(43/0/2 before), 39/0/9 on the synthetic path CI takes, and `make asan` 33/0/14.
Fuzzer and the 168 serve checks unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>